From f79193b540b94b447ee60d4ea944e95d9b696353 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Wed, 15 Jul 2026 16:49:51 +0000 Subject: [PATCH] Alphabetize behavior codes --- doc/src/tables/events.m4 | 129 ++++++++++++++++++++------------------- 1 file changed, 65 insertions(+), 64 deletions(-) diff --git a/doc/src/tables/events.m4 b/doc/src/tables/events.m4 index 0dafa53..45086ae 100644 --- a/doc/src/tables/events.m4 +++ b/doc/src/tables/events.m4 @@ -349,68 +349,6 @@ The following table lists these rules and implications: finished. -.. _EVENTS_utm_code: - -``sdb_utm`` (UTM Location) - A record of an individual's location recorded in UTM - coordinates. - - An individual can be located in only one place at any given - time.\ [#f1]_ - This means that the combination of |EVENTS.WID| and |EVENTS.Start| - must be unique. - - |_location_protocol| - - A related row should exist on |LOCATIONS_UTM|; there should be a - row on |LOCATIONS_UTM| with a |LOCATIONS_UTM|.\ |LOCATIONS_UTM.EID| - value of the event's |EVENTS.EID|. - There may be at most one of these related |LOCATIONS_UTM| rows. - The system will generate a warning when there is no |LOCATIONS_UTM| - row related to the event. - - The |ROLES| row related to the event, the row with a |ROLES|.\ - |ROLES.EID| value equal to the EVENTS.\ |EVENTS.EID| value, - designates the individual that was located. - There may be at most one |ROLES| row related to the UTM location - event. - The system will generate a warning when there is no |ROLES| row - related to the UTM location event. - - The individual located must be the individual the related |WATCHES| - row records as the located individual. - This means that the |ROLES| row related to the event must have a - |ROLES|.\ |ROLES.Participant| value equal to the |WATCHES|.\ - |WATCHES.AnimID| of the |WATCHES| row related to the UTM location - event. - - Both the EVENTS.\ |EVENTS.Start| and EVENTS.\ |EVENTS.Stop| - columns record the time the individual was at the recorded - location. - This means the value of the EVENTS.\ |EVENTS.Start| column must - equal the value of the EVENTS.\ |EVENTS.Stop| column. - - The time of the spatial recording is expected to correspond with a - time when a focal of a follow was under observation. - The system will generate a warning when there is not an |ARRIVALS| - related row that records the presence of a focal at the time the - spatial observation occurred. - This means that a warning will be generated when there is no - |WATCHES| row with a |WATCHES|.\ |WATCHES.Type| of ``sdb_brec``, a - |WATCHES|.\ |WATCHES.Date| and a |WATCHES|.\ |WATCHES.AnimID| that - match the date and individual of the location |WATCHES| row related - to the UTM event, and that |WATCHES| row does not have a related - EVENTS row where the |EVENTS.Behavior| code is ``sdb_arrival`` and - the EVENTS.\ |EVENTS.Start| value is less than or equal to the time - of the UTM location event value and the EVENTS.\ |EVENTS.Stop| - value is greater than or equal to the time of the location event, - and the event has a related |ROLES| row where the |ROLES|.\ - |ROLES.Participant| is the located individual. - - For UTM location events, the EVENTS.\ |EVENTS.Certainty| column - must be ``sdb_identity_certain``. - - .. _EVENTS_grooming_code: ``sdb_grooming`` (Grooming) @@ -665,6 +603,69 @@ The following table lists these rules and implications: For pantgrunt events, the EVENTS.\ |EVENTS.Certainty| column must be ``sdb_identity_certain``. + +.. _EVENTS_utm_code: + +``sdb_utm`` (UTM Location) + A record of an individual's location recorded in UTM + coordinates. + + An individual can be located in only one place at any given + time.\ [#f1]_ + This means that the combination of |EVENTS.WID| and |EVENTS.Start| + must be unique. + + |_location_protocol| + + A related row should exist on |LOCATIONS_UTM|; there should be a + row on |LOCATIONS_UTM| with a |LOCATIONS_UTM|.\ |LOCATIONS_UTM.EID| + value of the event's |EVENTS.EID|. + There may be at most one of these related |LOCATIONS_UTM| rows. + The system will generate a warning when there is no |LOCATIONS_UTM| + row related to the event. + + The |ROLES| row related to the event, the row with a |ROLES|.\ + |ROLES.EID| value equal to the EVENTS.\ |EVENTS.EID| value, + designates the individual that was located. + There may be at most one |ROLES| row related to the UTM location + event. + The system will generate a warning when there is no |ROLES| row + related to the UTM location event. + + The individual located must be the individual the related |WATCHES| + row records as the located individual. + This means that the |ROLES| row related to the event must have a + |ROLES|.\ |ROLES.Participant| value equal to the |WATCHES|.\ + |WATCHES.AnimID| of the |WATCHES| row related to the UTM location + event. + + Both the EVENTS.\ |EVENTS.Start| and EVENTS.\ |EVENTS.Stop| + columns record the time the individual was at the recorded + location. + This means the value of the EVENTS.\ |EVENTS.Start| column must + equal the value of the EVENTS.\ |EVENTS.Stop| column. + + The time of the spatial recording is expected to correspond with a + time when a focal of a follow was under observation. + The system will generate a warning when there is not an |ARRIVALS| + related row that records the presence of a focal at the time the + spatial observation occurred. + This means that a warning will be generated when there is no + |WATCHES| row with a |WATCHES|.\ |WATCHES.Type| of ``sdb_brec``, a + |WATCHES|.\ |WATCHES.Date| and a |WATCHES|.\ |WATCHES.AnimID| that + match the date and individual of the location |WATCHES| row related + to the UTM event, and that |WATCHES| row does not have a related + EVENTS row where the |EVENTS.Behavior| code is ``sdb_arrival`` and + the EVENTS.\ |EVENTS.Start| value is less than or equal to the time + of the UTM location event value and the EVENTS.\ |EVENTS.Stop| + value is greater than or equal to the time of the location event, + and the event has a related |ROLES| row where the |ROLES|.\ + |ROLES.Participant| is the located individual. + + For UTM location events, the EVENTS.\ |EVENTS.Certainty| column + must be ``sdb_identity_certain``. + + Aggressions may have no record of what time the aggression occurred. In this case the special value of ``sdb_no_time``, midnight, is recorded in the database.\ [#f2]_ @@ -753,8 +754,6 @@ The following table summarizes the available codes: +--------------------+--------------------------------+------------+------------+-------------------+----------------+---------------------+ | |spx_colobus| | Colobus encounter | - | Y | Y | - | |COLOBUS| | +--------------------+--------------------------------+------------+------------+-------------------+----------------+---------------------+ -| |spx_utm| | UTM location | - | - | - | Y | |LOCATIONS_UTM| | -+--------------------+--------------------------------+------------+------------+-------------------+----------------+---------------------+ | |spx_food| | Food bout | - | Y | Y | - | |FOOD_EVENTS| | +--------------------+--------------------------------+------------+------------+-------------------+----------------+---------------------+ | |spx_grooming| | Grooming | Y | Y | Y | - | |GROOMINGS| | @@ -770,6 +769,8 @@ The following table summarizes the available codes: +--------------------+--------------------------------+------------+------------+-------------------+----------------+---------------------+ | |spx_pg_event| | Pantgrunt | Y | Y | Y | - | |PANTGRUNTS| | +--------------------+--------------------------------+------------+------------+-------------------+----------------+---------------------+ +| |spx_utm| | UTM location | - | - | - | Y | |LOCATIONS_UTM| | ++--------------------+--------------------------------+------------+------------+-------------------+----------------+---------------------+ See :ref:`above ` for further detail regarding what related data each code requires, or is expected to have. -- 2.34.1